<!DOCTYPE html>
<html lang="en-US">

  <head>
    <meta charset="utf-8">
    <title>Apicurio Registry APIs</title>
    <link rel="stylesheet" type="text/css" href="/resources/css/apidocs.css" >
  </head>
  
  <body class="root">
    <div class="apidocs-header">
      <span class="title">- API Documentation</span>
    </div>
    <div class="apidocs-subheader">
      <span>Supported API Listing</span>
    </div>
    <div class="apidocs-body">
      <div class="apidocs-listing">
      
        <!-- Apicurio Registry API (v2) -->
        <div class="apidocs-api default">
          <div class="name">Core Registry API (Version 2)</div>
          <div class="description">
            The primary API for accessing Apicurio Registry.  This is the most recent API and is preferred for all use-cases.  All
            other APIs are supported for compatibility purposes only.
          </div>
          <div class="endpoint">
            <a href="/apis/registry/v2" class="url"><code>/apis/registry/v2</code></a>
          </div>
        </div>
      
        <!-- Apicurio Registry API (v1) -->
        <div class="apidocs-api deprecated">
          <div class="name">Core Registry API (Version 1)</div>
          <div class="description">
            The first version of the core Apicurio Registry API, this endpoint is supported to make upgrading consumers of the core
            registry API easier.  Old consumers that expect to interact with the Registry using the first version of the API can
            use this endpoint.
          </div>
          <div class="endpoint">
            <a href="/apis/registry/v1" class="url"><code>/apis/registry/v1</code></a>
          </div>
        </div>
        
        <!-- Confluent Compatible API (v6) -->
        <div class="apidocs-api">
          <div class="name">Confluent Schema Registry API (Version 6)</div>
          <div class="description">
            To provide compatibility with Confluent Serdes (and other clients), Apicurio Registry implements the API defined by
            the Confluent Schema Registry.  Use this endpoint if your tooling is compatible with v6 of that API.  This is only
            provided for compatibility purposes, the core Registry API should be used instead when possible.
          </div>
          <div class="endpoint">
            <a href="/apis/ccompat/v6" class="url"><code>/apis/ccompat/v6</code></a>
          </div>
        </div>
        
        <!-- IBM Compatible API (v6) -->
        <!--
        <div class="apidocs-api">
          <div class="name">IBM Schema Registry API (Version 1)</div>
          <div class="description">
            To provide compatibility with IBM toolchains (UI, Serdes, etc), Apicurio Registry implements the API defined by
            the IBM Schema Registry.  Use this endpoint if your tooling is compatible with the IBM Schema Registry API.
          </div>
          <div class="endpoint">
            <a href="/apis/ibmcompat/v1" class="url"><code>/apis/ibmcompat/v1</code></a>
          </div>
        </div>
         -->
        
        <!-- CNCF Schema Registry API (v0) -->
        <div class="apidocs-api">
          <div class="name">CNCF Schema Registry API (Version 0)</div>
          <div class="description">
            The CNCF community has worked to create an open standard for schema registries, for cloud events
            and for other use-cases.  Apicurio Registry implements the <a href="https://github.com/cloudevents/spec/blob/master/schemaregistry/schemaregistry.md">
            API defined by this work</a>.
          </div>
          <div class="endpoint">
            <a href="/apis/cncf/v0" class="url"><code>/apis/cncf/v0</code></a>
          </div>
        </div>
        
      </div>
    </div>
  </body>
</html>
